Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 711-tree-1
name: 1499
tree-preservation-order: undefined
711-tpo-1
uprn
address-text
point: POINT (-0.971463 50.866714)
geometry: MULTIPOLYGON (((-0.971406 50.866708,-0.971409 50.866719,-0.971417 50.866729,-0.971429 50.866737,-0.971445 50.866742,-0.971463 50.866744,-0.971480 50.866743,-0.971496 50.866738,-0.971509 50.866730,-0.971517 50.866720,-0.971520 50.866709,-0.971518 50.866698,-0.971510 50.866687,-0.971497 50.866679,-0.971482 50.866674,-0.971464 50.866672,-0.971446 50.866674,-0.971431 50.866679,-0.971418 50.866687,-0.971409 50.866697,-0.971406 50.866708)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL